Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 898-tree-1
name: 1499
tree-preservation-order: undefined
898-tpo-1
uprn
address-text
point: POINT (-0.970463 50.865003)
geometry: MULTIPOLYGON (((-0.970420 50.864999,-0.970422 50.865007,-0.970428 50.865015,-0.970437 50.865021,-0.970449 50.865025,-0.970462 50.865026,-0.970475 50.865025,-0.970487 50.865021,-0.970497 50.865015,-0.970503 50.865008,-0.970505 50.865000,-0.970504 50.864991,-0.970498 50.864984,-0.970488 50.864978,-0.970477 50.864974,-0.970463 50.864972,-0.970450 50.864973,-0.970438 50.864977,-0.970429 50.864983,-0.970422 50.864991,-0.970420 50.864999)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL